Skip to content

Replace implicits imports with syntax - #4917

Open
reardonj wants to merge 1 commit into
typelevel:mainfrom
reardonj:implicits-to-syntax
Open

reardonj wants to merge 1 commit into
typelevel:mainfrom
reardonj:implicits-to-syntax

Conversation

@reardonj

Copy link
Copy Markdown
Contributor

There are a lot of random code snippets and documentation that still suggests importing cats.implicits._ instead of cats.syntax.all._. This PR updates all of those. This was done as a straightforward search and replace.

I did skip changing the scalafix rules and old changelog entries to preserve historical accuracy, so there are still some usages, but there should be nothing left to point users at the old ways.

Comment thread docs/jump_start_guide.md

# Common issues

The Cats type class instances for standard library types are available in implicit scope and hence no longer have to be imported. If anything doesn't compile as expected, first make sure all the required Cats syntax implicits are in the scope — try importing ```cats.syntax.all._``` and see if the problem persists. The only exception is here is Cat's own ```Order``` and ```PartialOrder``` type classes which are available by importing ```cats.implicits._```.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed this sentence about Order and PartialOrder, as my understanding is the normal way to import these would be to just import cats.Order / cats.PartialOrder these days.

@reardonj
reardonj force-pushed the implicits-to-syntax branch from a43c1e0 to 8c6bd98 Compare November 10, 2026 12:53
@reardonj
reardonj force-pushed the implicits-to-syntax branch from 8c6bd98 to a805125 Compare November 10, 2026 12:54
@reardonj

Copy link
Copy Markdown
Contributor Author

I don't see any reason why this change should cause the native build to fail, but I don't have a system to reproduce :/

@satorg
satorg self-requested a review November 11, 2026 03:09
@satorg

satorg commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

I don't see any reason why this change should cause the native build to fail, but I don't have a system to reproduce :/

Tests in ScalaNative are flaky – it's a known yet very annoying issue.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants